Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5abf39c4533113dafed627f757c4fbe5265fb7f2f9cca3a80a301b20482d2225

Tx prefix hash: c2782c32b09ed022a440753fc1ba306923a94559581edbcf36a41f24bd24272c
Tx public key: 7c5e80f6f3fd3353bdcd113ee79a3a06df3fcb0ac6f8d295071c812b949f4d5b
Timestamp: 1723487588 Timestamp [UCT]: 2024-08-12 18:33:08 Age [y:d:h:m:s]: 00:285:03:46:53
Block: 1086473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203718 RingCT/type: yes/0
Extra: 017c5e80f6f3fd3353bdcd113ee79a3a06df3fcb0ac6f8d295071c812b949f4d5b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7211ea8fd4408f05569a752b7c90eac632ea2e2f3a8c2807b234ac20954c4f2 0.600000000000 1561070 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": 1086483, "vin": [ { "gen": { "height": 1086473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7211ea8fd4408f05569a752b7c90eac632ea2e2f3a8c2807b234ac20954c4f2" } } ], "extra": [ 1, 124, 94, 128, 246, 243, 253, 51, 83, 189, 205, 17, 62, 231, 154, 58, 6, 223, 63, 203, 10, 198, 248, 210, 149, 7, 28, 129, 43, 148, 159, 77, 91, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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