Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af0c65fe328b32ad7cfef64f2724371bfea38c80a5bde78a6b8b8f1f7fec34ab

Tx prefix hash: 2b7384aefe92b533681c3fbfa339907e04c8fe39f3577b9142b487c88bb543c8
Tx public key: dbb7b14c28399752102c85aa2aae1062fe0e4f2879593df46422ec9c5c5a059d
Timestamp: 1713897321 Timestamp [UCT]: 2024-04-23 18:35:21 Age [y:d:h:m:s]: 00:307:11:42:45
Block: 1006965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219775 RingCT/type: yes/0
Extra: 01dbb7b14c28399752102c85aa2aae1062fe0e4f2879593df46422ec9c5c5a059d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a42f41fe16e22f9b1c73501cf27a2625d78993e299a5874753ee8274ddd680b 0.600000000000 1468163 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": 1006975, "vin": [ { "gen": { "height": 1006965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a42f41fe16e22f9b1c73501cf27a2625d78993e299a5874753ee8274ddd680b" } } ], "extra": [ 1, 219, 183, 177, 76, 40, 57, 151, 82, 16, 44, 133, 170, 42, 174, 16, 98, 254, 14, 79, 40, 121, 89, 61, 244, 100, 34, 236, 156, 92, 90, 5, 157, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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