Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f12ffa71bb4cbca99bd296ff2d5760461d4abb9b5fd62add2fdd1c55caf5fdbd

Tx prefix hash: a622fa5ab50984a76a491ec2cf80a454d72418c4fa430795729641997e0a2dc3
Tx public key: 5a141e0e37bbe61e4a404bc46fc8596432aa8e1cddba4ae49763ae02094221b1
Timestamp: 1723850142 Timestamp [UCT]: 2024-08-16 23:15:42 Age [y:d:h:m:s]: 00:242:16:20:45
Block: 1089479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173324 RingCT/type: yes/0
Extra: 015a141e0e37bbe61e4a404bc46fc8596432aa8e1cddba4ae49763ae02094221b1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7a3ba8d1b5b9b196d2d72938ab1ba654d93caf31e34190f15886c153b7bdf21 0.600000000000 1564100 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": 1089489, "vin": [ { "gen": { "height": 1089479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7a3ba8d1b5b9b196d2d72938ab1ba654d93caf31e34190f15886c153b7bdf21" } } ], "extra": [ 1, 90, 20, 30, 14, 55, 187, 230, 30, 74, 64, 75, 196, 111, 200, 89, 100, 50, 170, 142, 28, 221, 186, 74, 228, 151, 99, 174, 2, 9, 66, 33, 177, 2, 17, 0, 0, 0, 5, 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