Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6570fd27056c33a25e27f1ecc68450d55917213ee7ff64af1b84206570b3e327

Tx prefix hash: 3915121f614268f644663e5e2b51b05309e63e930e16032e58474b96d027a0be
Tx public key: d0ea9957f4cf98b4a3801f28460ba656d6cba773f87f00b4cfec18d383375407
Timestamp: 1577672615 Timestamp [UCT]: 2019-12-30 02:23:35 Age [y:d:h:m:s]: 05:044:12:07:59
Block: 34714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181561 RingCT/type: yes/0
Extra: 01d0ea9957f4cf98b4a3801f28460ba656d6cba773f87f00b4cfec18d383375407021100000004d81c26c0000000000000000000

1 output(s) for total of 470.954512955000 dcy

stealth address amount amount idx
00: 2cf0c3bd613ec21697d19da7cc31c1e21a23e472134e4461cc9f2a64a3c7fa01 470.954512955000 58458 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": 34724, "vin": [ { "gen": { "height": 34714 } } ], "vout": [ { "amount": 470954512955, "target": { "key": "2cf0c3bd613ec21697d19da7cc31c1e21a23e472134e4461cc9f2a64a3c7fa01" } } ], "extra": [ 1, 208, 234, 153, 87, 244, 207, 152, 180, 163, 128, 31, 40, 70, 11, 166, 86, 214, 203, 167, 115, 248, 127, 0, 180, 207, 236, 24, 211, 131, 55, 84, 7, 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