Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19fb47067fe9627f2984e1fbe6068567943549d87c99ba43b008b28a2a26efcd

Tx prefix hash: 43e406e6c4c510c3a1ad94adf40898ad0b997ac43fbabb3d1de41ef2218bc7bc
Tx public key: e3b7116abd8fb95bbafb2d65f8c6f10fdc104c9c335b12b380112acb1ca6c6ec
Timestamp: 1737787620 Timestamp [UCT]: 2025-01-25 06:47:00 Age [y:d:h:m:s]: 00:143:11:40:15
Block: 1204831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102284 RingCT/type: yes/0
Extra: 01e3b7116abd8fb95bbafb2d65f8c6f10fdc104c9c335b12b380112acb1ca6c6ec0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88d17279dc0873602a8745048b2612783e768a795ccd5d0f617d07ae45f3edcb 0.600000000000 1691524 of 15

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": 1204841, "vin": [ { "gen": { "height": 1204831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88d17279dc0873602a8745048b2612783e768a795ccd5d0f617d07ae45f3edcb" } } ], "extra": [ 1, 227, 183, 17, 106, 189, 143, 185, 91, 186, 251, 45, 101, 248, 198, 241, 15, 220, 16, 76, 156, 51, 91, 18, 179, 128, 17, 42, 203, 28, 166, 198, 236, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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