Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3939576f52c75671ef5726e184b1dff82b4ba239a16b397b5251ea152d1409bd

Tx prefix hash: 7c9ba8af399cf03a489e7d2aaf23395ac8065a443a6c7d2d35f503d4a8385f7a
Tx public key: 1e8ca4171d124f8624bbb24eeedf5f8b5a0faea8019ec04d3ee7a02a14be3822
Timestamp: 1737127294 Timestamp [UCT]: 2025-01-17 15:21:34 Age [y:d:h:m:s]: 00:151:11:10:11
Block: 1199390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107966 RingCT/type: yes/0
Extra: 011e8ca4171d124f8624bbb24eeedf5f8b5a0faea8019ec04d3ee7a02a14be38220211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8889d5f80984ecd0393ce489e3976e56053f46f407b69014b20c740e56a2b68 0.600000000000 1686021 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": 1199400, "vin": [ { "gen": { "height": 1199390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8889d5f80984ecd0393ce489e3976e56053f46f407b69014b20c740e56a2b68" } } ], "extra": [ 1, 30, 140, 164, 23, 29, 18, 79, 134, 36, 187, 178, 78, 238, 223, 95, 139, 90, 15, 174, 168, 1, 158, 192, 77, 62, 231, 160, 42, 20, 190, 56, 34, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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