Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e70f424b77b7edfe642c586823ab1da84096c3e9d374ad3b553e2159df1a28f1

Tx prefix hash: 1feaf1d9857be647582e866eed6185ce7f5a4a44f1d354d540f486ff0e17f759
Tx public key: b64d0a2f5a97bfa3fd38b856a03859480543197cba03e0a8060f52a880e294ab
Timestamp: 1716504550 Timestamp [UCT]: 2024-05-23 22:49:10 Age [y:d:h:m:s]: 00:243:21:04:00
Block: 1028581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174484 RingCT/type: yes/0
Extra: 01b64d0a2f5a97bfa3fd38b856a03859480543197cba03e0a8060f52a880e294ab02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38dfde2cffc056b77351068561bd659c794687fe00f3e11971fdcd0806f152d4 0.600000000000 1496574 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": 1028591, "vin": [ { "gen": { "height": 1028581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38dfde2cffc056b77351068561bd659c794687fe00f3e11971fdcd0806f152d4" } } ], "extra": [ 1, 182, 77, 10, 47, 90, 151, 191, 163, 253, 56, 184, 86, 160, 56, 89, 72, 5, 67, 25, 124, 186, 3, 224, 168, 6, 15, 82, 168, 128, 226, 148, 171, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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