Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1605795bee3f773272ea9d7395b07b39a9d9dcb7a50da4b70491b5f9c8d2483b

Tx prefix hash: 51881a0152610aacc2992277c3547e949923478c3611e8eee82b9cc9167fcb06
Tx public key: 3d71b8a4d508c79dee70baefb3386bff024fc612fad44937145ed2420c484f8a
Timestamp: 1721333113 Timestamp [UCT]: 2024-07-18 20:05:13 Age [y:d:h:m:s]: 00:177:13:25:05
Block: 1068622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127031 RingCT/type: yes/0
Extra: 013d71b8a4d508c79dee70baefb3386bff024fc612fad44937145ed2420c484f8a02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1d520d3249662c07be89f2e9e07a4d9a55799efb910cec580226be6eef988cc 0.600000000000 1539723 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": 1068632, "vin": [ { "gen": { "height": 1068622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1d520d3249662c07be89f2e9e07a4d9a55799efb910cec580226be6eef988cc" } } ], "extra": [ 1, 61, 113, 184, 164, 213, 8, 199, 157, 238, 112, 186, 239, 179, 56, 107, 255, 2, 79, 198, 18, 250, 212, 73, 55, 20, 94, 210, 66, 12, 72, 79, 138, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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