Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd02f65053ed2331bf9d8812628e6c640989f7f20501c1bcc27a5f0971b68de7

Tx prefix hash: ef2b8ee7dc45ad4b33b62e77e864d93000837941a83a7c8d35870dcc12e9725b
Tx public key: b37d1f0b8069ed635b9bec8afb6e60c957d71a39ebd0e44fcd3fc7f676e734aa
Timestamp: 1716132042 Timestamp [UCT]: 2024-05-19 15:20:42 Age [y:d:h:m:s]: 00:301:21:10:12
Block: 1025488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215781 RingCT/type: yes/0
Extra: 01b37d1f0b8069ed635b9bec8afb6e60c957d71a39ebd0e44fcd3fc7f676e734aa02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8a31c779c727f821479d88973db3865e69dc8f403d7931411594c85fa138c62 0.600000000000 1492035 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": 1025498, "vin": [ { "gen": { "height": 1025488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8a31c779c727f821479d88973db3865e69dc8f403d7931411594c85fa138c62" } } ], "extra": [ 1, 179, 125, 31, 11, 128, 105, 237, 99, 91, 155, 236, 138, 251, 110, 96, 201, 87, 215, 26, 57, 235, 208, 228, 79, 205, 63, 199, 246, 118, 231, 52, 170, 2, 17, 0, 0, 0, 5, 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