Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b0105dace1df9c056899602894ac91a3c7f20e36027ea628346724de1f1980a

Tx prefix hash: 2535dd2e2265917ba4fc6fc57cd5d983eb9c94fab6eea5a3b2c08d20f52bb1ad
Tx public key: b2abc42d1d23553fc7c4c1326a9bdf5c5ec6ee0f605dbbd2ac5a82304d3388ff
Timestamp: 1720613861 Timestamp [UCT]: 2024-07-10 12:17:41 Age [y:d:h:m:s]: 00:164:02:34:22
Block: 1062651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117458 RingCT/type: yes/0
Extra: 01b2abc42d1d23553fc7c4c1326a9bdf5c5ec6ee0f605dbbd2ac5a82304d3388ff02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1693a33001f55a6615e8f5b71f11886f737c49f32da60b8ea263f24072ecbd06 0.600000000000 1533156 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": 1062661, "vin": [ { "gen": { "height": 1062651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1693a33001f55a6615e8f5b71f11886f737c49f32da60b8ea263f24072ecbd06" } } ], "extra": [ 1, 178, 171, 196, 45, 29, 35, 85, 63, 199, 196, 193, 50, 106, 155, 223, 92, 94, 198, 238, 15, 96, 93, 187, 210, 172, 90, 130, 48, 77, 51, 136, 255, 2, 17, 0, 0, 0, 11, 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