Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d18aabb08ac4669056d7cf611d745346e326e1bfc271566d60f3cc45bd7a491f

Tx prefix hash: 572193cac2c75f513eda64e09b4fe881806382304d1e70ea2c54773b1a99479e
Tx public key: 5aa39e0017a7b8939614a9e8cf5cf918a3614be590894fab05da07d086fd2bb5
Timestamp: 1736910872 Timestamp [UCT]: 2025-01-15 03:14:32 Age [y:d:h:m:s]: 00:155:22:17:31
Block: 1197607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111126 RingCT/type: yes/0
Extra: 015aa39e0017a7b8939614a9e8cf5cf918a3614be590894fab05da07d086fd2bb50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abd364642b1a15755c78078f38d9783de8264093f9f6309262f9891ed7a74a3e 0.600000000000 1684220 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": 1197617, "vin": [ { "gen": { "height": 1197607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abd364642b1a15755c78078f38d9783de8264093f9f6309262f9891ed7a74a3e" } } ], "extra": [ 1, 90, 163, 158, 0, 23, 167, 184, 147, 150, 20, 169, 232, 207, 92, 249, 24, 163, 97, 75, 229, 144, 137, 79, 171, 5, 218, 7, 208, 134, 253, 43, 181, 2, 17, 0, 0, 0, 3, 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