Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c878fe40125d96c5f8f09493e7e4b7bb1d121949a5b29b3788c6e6c523f7b45e

Tx prefix hash: 5b85d4cb2792dc332a76c13021fc7820cc58cb4045e3b303bcd767982b05a5ff
Tx public key: 25f1a48eb79476cba99b400b3aec3e21f444fc53290c07dc419b7684daa2534c
Timestamp: 1732430588 Timestamp [UCT]: 2024-11-24 06:43:08 Age [y:d:h:m:s]: 00:139:23:02:56
Block: 1160510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99846 RingCT/type: yes/0
Extra: 0125f1a48eb79476cba99b400b3aec3e21f444fc53290c07dc419b7684daa2534c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 470bc25459c29e4054fd7bed8c947ae2e5e89f388b28db8527e10c08c31179be 0.600000000000 1646157 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": 1160520, "vin": [ { "gen": { "height": 1160510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "470bc25459c29e4054fd7bed8c947ae2e5e89f388b28db8527e10c08c31179be" } } ], "extra": [ 1, 37, 241, 164, 142, 183, 148, 118, 203, 169, 155, 64, 11, 58, 236, 62, 33, 244, 68, 252, 83, 41, 12, 7, 220, 65, 155, 118, 132, 218, 162, 83, 76, 2, 17, 0, 0, 0, 1, 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