Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ac0690ea6a1d5704e61bd9db7ce84da505c03c434a53457559081c35838597

Tx prefix hash: a0844d140bc1babbc5f0430417e2ae77d7d004454656c2337cb82e1f32d18379
Tx public key: e5b9fa4e67d420a9d9f7dcbe3686fed9f4e3c184615a0a1c9670158b5815d54c
Timestamp: 1734116659 Timestamp [UCT]: 2024-12-13 19:04:19 Age [y:d:h:m:s]: 00:110:13:59:19
Block: 1174501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78800 RingCT/type: yes/0
Extra: 01e5b9fa4e67d420a9d9f7dcbe3686fed9f4e3c184615a0a1c9670158b5815d54c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1a742abaa760e5a16b47ee35ce1a4ce2b138b8c082fd428ec5172091c2cca51 0.600000000000 1660660 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": 1174511, "vin": [ { "gen": { "height": 1174501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1a742abaa760e5a16b47ee35ce1a4ce2b138b8c082fd428ec5172091c2cca51" } } ], "extra": [ 1, 229, 185, 250, 78, 103, 212, 32, 169, 217, 247, 220, 190, 54, 134, 254, 217, 244, 227, 193, 132, 97, 90, 10, 28, 150, 112, 21, 139, 88, 21, 213, 76, 2, 17, 0, 0, 0, 2, 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