Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f833ca1e0e57f86c8c0e40814a472a860a789a3ff6d9092d8381d2d5ed93eac9

Tx prefix hash: 973de64f1680e2a5f2364e2a0610753604893fecbf9981ba3b361dec6f6fd3c5
Tx public key: 9ae6188359fe94ed605d0384aa3400ff3d3352fa5d678a6095de0909d97b2d7f
Timestamp: 1636675001 Timestamp [UCT]: 2021-11-11 23:56:41 Age [y:d:h:m:s]: 03:017:11:18:19
Block: 372435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 791076 RingCT/type: yes/0
Extra: 019ae6188359fe94ed605d0384aa3400ff3d3352fa5d678a6095de0909d97b2d7f021100000001a272b9cb000000000000000000

1 output(s) for total of 35.808297247000 dcy

stealth address amount amount idx
00: e2d7570ed269b1ce735217563f722db104cfaba9274f9485e306664d8ada3ca6 35.808297247000 754443 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 372445, "vin": [ { "gen": { "height": 372435 } } ], "vout": [ { "amount": 35808297247, "target": { "key": "e2d7570ed269b1ce735217563f722db104cfaba9274f9485e306664d8ada3ca6" } } ], "extra": [ 1, 154, 230, 24, 131, 89, 254, 148, 237, 96, 93, 3, 132, 170, 52, 0, 255, 61, 51, 82, 250, 93, 103, 138, 96, 149, 222, 9, 9, 217, 123, 45, 127, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8