Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a3562aa71f42490b2abd113bc3500edb2ddab46a546a4888ceb27677e0c2e9b

Tx prefix hash: 319e3121835c3a6da91561acc47acda887485e0c4f297ae67ebcf869126723de
Tx public key: 72f0770df7d6e97c8a3a78bc3042dfb0086d698ae28fe993b4e388da567b3acd
Timestamp: 1701894801 Timestamp [UCT]: 2023-12-06 20:33:21 Age [y:d:h:m:s]: 01:118:01:54:17
Block: 907452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345531 RingCT/type: yes/0
Extra: 0172f0770df7d6e97c8a3a78bc3042dfb0086d698ae28fe993b4e388da567b3acd02110000000233af99f4000000000000000000

1 output(s) for total of 0.604275234000 dcy

stealth address amount amount idx
00: 0be64a90eae61bdacfcb6b0edad578118afd7afd3cf5f11998374dad03abb5d9 0.604275234000 1364441 of 0

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": 907462, "vin": [ { "gen": { "height": 907452 } } ], "vout": [ { "amount": 604275234, "target": { "key": "0be64a90eae61bdacfcb6b0edad578118afd7afd3cf5f11998374dad03abb5d9" } } ], "extra": [ 1, 114, 240, 119, 13, 247, 214, 233, 124, 138, 58, 120, 188, 48, 66, 223, 176, 8, 109, 105, 138, 226, 143, 233, 147, 180, 227, 136, 218, 86, 123, 58, 205, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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