Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5719e6514ccff2bd0999a2fcd8058737426777d85cdaaf05931c6f6d4029ec8

Tx prefix hash: 74134ba7ab3e96fc7df80bba108cb63dbc85ddf1d02637343665f75712d8c876
Tx public key: cf9883b3bf0e6e3567c9d72b941ceab5ecee29c6a36abf1464a070c6061e31fc
Timestamp: 1578940815 Timestamp [UCT]: 2020-01-13 18:40:15 Age [y:d:h:m:s]: 05:051:13:10:34
Block: 44881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186934 RingCT/type: yes/0
Extra: 01cf9883b3bf0e6e3567c9d72b941ceab5ecee29c6a36abf1464a070c6061e31fc021100000004d81c26c0000000000000000000

1 output(s) for total of 435.804245269000 dcy

stealth address amount amount idx
00: 01cdba118b4689795750f3a9bfdabaf0f3d98c5a667100d207482cd6fb084121 435.804245269000 81818 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": 44891, "vin": [ { "gen": { "height": 44881 } } ], "vout": [ { "amount": 435804245269, "target": { "key": "01cdba118b4689795750f3a9bfdabaf0f3d98c5a667100d207482cd6fb084121" } } ], "extra": [ 1, 207, 152, 131, 179, 191, 14, 110, 53, 103, 201, 215, 43, 148, 28, 234, 181, 236, 238, 41, 198, 163, 106, 191, 20, 100, 160, 112, 198, 6, 30, 49, 252, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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