Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a5014e831736d25d2385ed739a9371a2ac038cbd15d31a02bf1627afc1facd2

Tx prefix hash: ff595b5dfe21da5e35e7a092aba442fdda2d535627a9112f51362cf214079483
Tx public key: 8df2aa287891ce43676e1de3780864d254f2f9e4321889a7162bcc6e38a617a3
Timestamp: 1730321939 Timestamp [UCT]: 2024-10-30 20:58:59 Age [y:d:h:m:s]: 00:148:20:00:36
Block: 1143057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106193 RingCT/type: yes/0
Extra: 018df2aa287891ce43676e1de3780864d254f2f9e4321889a7162bcc6e38a617a3021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eee7a53324b4a3e870d5bf037b3e42d66cc7424d8f990c3d9060748f3469eba5 0.600000000000 1626916 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": 1143067, "vin": [ { "gen": { "height": 1143057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eee7a53324b4a3e870d5bf037b3e42d66cc7424d8f990c3d9060748f3469eba5" } } ], "extra": [ 1, 141, 242, 170, 40, 120, 145, 206, 67, 103, 110, 29, 227, 120, 8, 100, 210, 84, 242, 249, 228, 50, 24, 137, 167, 22, 43, 204, 110, 56, 166, 23, 163, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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