Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 622db6c61ebaf036f22017852d4e90ae02a969f6f759b55fd1665777c7f22171

Tx prefix hash: 79f94c87405b7d56513cde1b388a6268331f2fd3d4dc129def3eb75e595806cc
Tx public key: 5c58b1534ddce0e054db3746b5dc9652b2d24be4025edfa64244fa73b2e8f6bf
Timestamp: 1574105465 Timestamp [UCT]: 2019-11-18 19:31:05 Age [y:d:h:m:s]: 04:353:18:22:22
Block: 12098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1135029 RingCT/type: yes/0
Extra: 015c58b1534ddce0e054db3746b5dc9652b2d24be4025edfa64244fa73b2e8f6bf021100000001ccefb800000000000000000000

1 output(s) for total of 559.648304397000 dcy

stealth address amount amount idx
00: 8d0cd1ff21a12108bd1e1cfb8d19d598bf996850a77e5a5636edd711dd3ef416 559.648304397000 13185 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": 12108, "vin": [ { "gen": { "height": 12098 } } ], "vout": [ { "amount": 559648304397, "target": { "key": "8d0cd1ff21a12108bd1e1cfb8d19d598bf996850a77e5a5636edd711dd3ef416" } } ], "extra": [ 1, 92, 88, 177, 83, 77, 220, 224, 224, 84, 219, 55, 70, 181, 220, 150, 82, 178, 210, 75, 228, 2, 94, 223, 166, 66, 68, 250, 115, 178, 232, 246, 191, 2, 17, 0, 0, 0, 1, 204, 239, 184, 0, 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