Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eece93602996f153b3831a81105fae0b8a221bef5dd9f98ceae24d0d66e5d9e

Tx prefix hash: c14bc3e890c04fa20e72bb2a3819ec4fb3586fb4e98813d898a5ef13c05717fc
Tx public key: 293e478e3bcd4025acecf4aee179f0db1b13364e9794fe2e0c533ad8170d72e2
Timestamp: 1722914435 Timestamp [UCT]: 2024-08-06 03:20:35 Age [y:d:h:m:s]: 00:292:13:34:45
Block: 1081712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209040 RingCT/type: yes/0
Extra: 01293e478e3bcd4025acecf4aee179f0db1b13364e9794fe2e0c533ad8170d72e2021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 347ffb1d6e8952b062850421bfeaeff05b2ad6e47faa868d8b49fb1a1149a9f9 0.600000000000 1555533 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": 1081722, "vin": [ { "gen": { "height": 1081712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "347ffb1d6e8952b062850421bfeaeff05b2ad6e47faa868d8b49fb1a1149a9f9" } } ], "extra": [ 1, 41, 62, 71, 142, 59, 205, 64, 37, 172, 236, 244, 174, 225, 121, 240, 219, 27, 19, 54, 78, 151, 148, 254, 46, 12, 83, 58, 216, 23, 13, 114, 226, 2, 17, 0, 0, 0, 1, 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