Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74d564e5326fe1047d47c65ceba3e6a7056d6a888807d4a68af55ebc92befad5

Tx prefix hash: b862b3e71ad59cd614a287f74e07faf228646e6324cf8c889fe905e1e8dacf4b
Tx public key: d8472e6c452f8faad79f3948c01c4293a5d17c79201765b7d4a82dc1456b14f7
Timestamp: 1725786473 Timestamp [UCT]: 2024-09-08 09:07:53 Age [y:d:h:m:s]: 01:059:18:43:06
Block: 1105525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301144 RingCT/type: yes/0
Extra: 01d8472e6c452f8faad79f3948c01c4293a5d17c79201765b7d4a82dc1456b14f702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37ffeb1690b03197e0cbf973d46c70a868dada9a9cc6479a4034dc4f001e9b9d 0.600000000000 1582884 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": 1105535, "vin": [ { "gen": { "height": 1105525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37ffeb1690b03197e0cbf973d46c70a868dada9a9cc6479a4034dc4f001e9b9d" } } ], "extra": [ 1, 216, 71, 46, 108, 69, 47, 143, 170, 215, 159, 57, 72, 192, 28, 66, 147, 165, 209, 124, 121, 32, 23, 101, 183, 212, 168, 45, 193, 69, 107, 20, 247, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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