Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf2f48a88909d21bbe538fbe162606f4de30ae1346b9f53484535af418cb3cbb

Tx prefix hash: 4e29e751a53d87f28d9e5634b0767ed6887ba09e180380e8a42e31f0be527225
Tx public key: 440e6334c04ad8027a6a12471a39b5c91c51c9c876f73f2858e36a1e86447106
Timestamp: 1731615821 Timestamp [UCT]: 2024-11-14 20:23:41 Age [y:d:h:m:s]: 00:133:05:23:02
Block: 1153768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95032 RingCT/type: yes/0
Extra: 01440e6334c04ad8027a6a12471a39b5c91c51c9c876f73f2858e36a1e86447106021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e79ee1e7472d4cc4496132a61754b044de8c3d1eecd3de1c48905e4c8229e0a 0.600000000000 1639379 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": 1153778, "vin": [ { "gen": { "height": 1153768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e79ee1e7472d4cc4496132a61754b044de8c3d1eecd3de1c48905e4c8229e0a" } } ], "extra": [ 1, 68, 14, 99, 52, 192, 74, 216, 2, 122, 106, 18, 71, 26, 57, 181, 201, 28, 81, 201, 200, 118, 247, 63, 40, 88, 227, 106, 30, 134, 68, 113, 6, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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