Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 528fd601432270c5f3ed89d7918f4e2ff9c069fb881879a02f291b4e88a20d63

Tx prefix hash: ebec330c3ae56d01c7ad22db5969074f03ff05a664c89b335c512b6bec192d02
Tx public key: edcebc469ce4bf6a17fd35d336d0d78660e1ad1ce7140ba95b56f10bbc045f85
Timestamp: 1657109406 Timestamp [UCT]: 2022-07-06 12:10:06 Age [y:d:h:m:s]: 03:117:18:44:18
Block: 537858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863905 RingCT/type: yes/0
Extra: 01edcebc469ce4bf6a17fd35d336d0d78660e1ad1ce7140ba95b56f10bbc045f8502110000000f4da16a3a000000000000000000

1 output(s) for total of 10.135690033000 dcy

stealth address amount amount idx
00: e2aaf7455789ab775cc15914ad8148d74d3d2d56e1104c7b70e51fb095525597 10.135690033000 967791 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": 537868, "vin": [ { "gen": { "height": 537858 } } ], "vout": [ { "amount": 10135690033, "target": { "key": "e2aaf7455789ab775cc15914ad8148d74d3d2d56e1104c7b70e51fb095525597" } } ], "extra": [ 1, 237, 206, 188, 70, 156, 228, 191, 106, 23, 253, 53, 211, 54, 208, 215, 134, 96, 225, 173, 28, 231, 20, 11, 169, 91, 86, 241, 11, 188, 4, 95, 133, 2, 17, 0, 0, 0, 15, 77, 161, 106, 58, 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