Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 884d9dda0af780b9c5b13f36ae7ee4f4bb0463c503a5f4d33f3ae81424809722

Tx prefix hash: 63dbfeb95e9edb959c557093bd29d6b2345ef27b2b137a8fb5a7fcd8e2ada433
Tx public key: e6d7fff5898c56e7270e9ff9f64a4d5deb20258080ced3a3c9040162d41ca548
Timestamp: 1719971772 Timestamp [UCT]: 2024-07-03 01:56:12 Age [y:d:h:m:s]: 00:271:04:22:23
Block: 1057314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193759 RingCT/type: yes/0
Extra: 01e6d7fff5898c56e7270e9ff9f64a4d5deb20258080ced3a3c9040162d41ca5480211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6c35f5fe805f54d784c6da897ac94dcc64d7222c20617688f8a60faf563e4f3 0.600000000000 1527749 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": 1057324, "vin": [ { "gen": { "height": 1057314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6c35f5fe805f54d784c6da897ac94dcc64d7222c20617688f8a60faf563e4f3" } } ], "extra": [ 1, 230, 215, 255, 245, 137, 140, 86, 231, 39, 14, 159, 249, 246, 74, 77, 93, 235, 32, 37, 128, 128, 206, 211, 163, 201, 4, 1, 98, 212, 28, 165, 72, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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