Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b973d178c704ecf4122f172c94c31e7e0c450b963419e056934fb002a0e7b9f4

Tx prefix hash: 182d5da86aaba6f92c75beba2d713cdd582af8d4afed4e6722c94d017b5cd51a
Tx public key: 9d70ab36323192730dadce7a6e1a142f3d8a9956cfce2d8026e648bff12e298c
Timestamp: 1701414443 Timestamp [UCT]: 2023-12-01 07:07:23 Age [y:d:h:m:s]: 01:164:04:59:56
Block: 903467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378543 RingCT/type: yes/0
Extra: 019d70ab36323192730dadce7a6e1a142f3d8a9956cfce2d8026e648bff12e298c021100000001679a8a81000000000000000000

1 output(s) for total of 0.622929302000 dcy

stealth address amount amount idx
00: 613f13f3a278cae36ef38cbb358389fd733fab86b23a3524546f1c179a63e257 0.622929302000 1360146 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": 903477, "vin": [ { "gen": { "height": 903467 } } ], "vout": [ { "amount": 622929302, "target": { "key": "613f13f3a278cae36ef38cbb358389fd733fab86b23a3524546f1c179a63e257" } } ], "extra": [ 1, 157, 112, 171, 54, 50, 49, 146, 115, 13, 173, 206, 122, 110, 26, 20, 47, 61, 138, 153, 86, 207, 206, 45, 128, 38, 230, 72, 191, 241, 46, 41, 140, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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