Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7e84dee9f88855b22ccb250a71cdf1abdafd4688f8b1ab643aa57255605898b

Tx prefix hash: 081ea545cbd67a62372d9ecb2640846db4565683af64a817a305c9c96bdfaf92
Tx public key: 01e47a7f1ad9ad1b9cc7ca446b76a2d4d98bb39868c69e1a57ea4e92f2458879
Timestamp: 1714822357 Timestamp [UCT]: 2024-05-04 11:32:37 Age [y:d:h:m:s]: 00:330:18:07:33
Block: 1014633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236423 RingCT/type: yes/0
Extra: 0101e47a7f1ad9ad1b9cc7ca446b76a2d4d98bb39868c69e1a57ea4e92f245887902110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 738067472852fd8048e98d5bfd287a31ab53a77e5947b96397482c30d4928191 0.600000000000 1477778 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": 1014643, "vin": [ { "gen": { "height": 1014633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "738067472852fd8048e98d5bfd287a31ab53a77e5947b96397482c30d4928191" } } ], "extra": [ 1, 1, 228, 122, 127, 26, 217, 173, 27, 156, 199, 202, 68, 107, 118, 162, 212, 217, 139, 179, 152, 104, 198, 158, 26, 87, 234, 78, 146, 242, 69, 136, 121, 2, 17, 0, 0, 0, 8, 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