Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f287ddffe23ea51cef0d1c82e46a6bcb281e7de0f608ac5bb54c7643ebe077d5

Tx prefix hash: df4d8187330a4a914deaa48e2ffe66f5617d788f97101e96640ebaab41c6981e
Tx public key: 1e4c1f625dee0a7c6285ab869168f1e36a7d2a1d80099641003059c119f257eb
Timestamp: 1733213850 Timestamp [UCT]: 2024-12-03 08:17:30 Age [y:d:h:m:s]: 00:111:06:05:26
Block: 1167003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79309 RingCT/type: yes/0
Extra: 011e4c1f625dee0a7c6285ab869168f1e36a7d2a1d80099641003059c119f257eb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6677fa207af1e8fe57323f3cbce2be72ad049fca5d00ec200db54a83466d1f4 0.600000000000 1652696 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": 1167013, "vin": [ { "gen": { "height": 1167003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6677fa207af1e8fe57323f3cbce2be72ad049fca5d00ec200db54a83466d1f4" } } ], "extra": [ 1, 30, 76, 31, 98, 93, 238, 10, 124, 98, 133, 171, 134, 145, 104, 241, 227, 106, 125, 42, 29, 128, 9, 150, 65, 0, 48, 89, 193, 25, 242, 87, 235, 2, 17, 0, 0, 0, 3, 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