Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aca2c9354d022d3004214d3c176466aefc2fa67b0af858ec15cc29d9aaadc7fe

Tx prefix hash: b82ebdcdd30183402c8b87af50bae5941dc9233ebef51735c30a2d3c6ff25bcd
Tx public key: 114b5a35d859735d3f5ddc2f50362de990656a38b07fc9c3fa8622a68e17b3a5
Timestamp: 1705097603 Timestamp [UCT]: 2024-01-12 22:13:23 Age [y:d:h:m:s]: 01:308:06:13:33
Block: 933989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479150 RingCT/type: yes/0
Extra: 01114b5a35d859735d3f5ddc2f50362de990656a38b07fc9c3fa8622a68e17b3a50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec4b8d378fe216b5584861be49d9c3e974e3b5b1acb59879cde9bc181366d6f9 0.600000000000 1391973 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": 933999, "vin": [ { "gen": { "height": 933989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec4b8d378fe216b5584861be49d9c3e974e3b5b1acb59879cde9bc181366d6f9" } } ], "extra": [ 1, 17, 75, 90, 53, 216, 89, 115, 93, 63, 93, 220, 47, 80, 54, 45, 233, 144, 101, 106, 56, 176, 127, 201, 195, 250, 134, 34, 166, 142, 23, 179, 165, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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