Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d59f826dc117066a8e61ce9c65f686b45580576a956fbcea80f813bd91ffd255

Tx prefix hash: d54154e0d6f4eb670dab0566abdfec7a01a120b88e9f80c5e99eb3b51287c7aa
Tx public key: d1132a462891ac0332868c2b7a4792223039cc33dc1055f23dfe2cf81d824fd1
Timestamp: 1724516165 Timestamp [UCT]: 2024-08-24 16:16:05 Age [y:d:h:m:s]: 00:222:09:30:32
Block: 1095027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158767 RingCT/type: yes/0
Extra: 01d1132a462891ac0332868c2b7a4792223039cc33dc1055f23dfe2cf81d824fd102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a4dd541ccfe6509a7ea69db82b57982d80e52c937f3de4b5514b5b1d426e19f 0.600000000000 1570156 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": 1095037, "vin": [ { "gen": { "height": 1095027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a4dd541ccfe6509a7ea69db82b57982d80e52c937f3de4b5514b5b1d426e19f" } } ], "extra": [ 1, 209, 19, 42, 70, 40, 145, 172, 3, 50, 134, 140, 43, 122, 71, 146, 34, 48, 57, 204, 51, 220, 16, 85, 242, 61, 254, 44, 248, 29, 130, 79, 209, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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