Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a90b4be0ba5b09042d340fa8e04d9d268092a187c3371f47e88a0540dbb026d4

Tx prefix hash: c30a653560c6e1cdca60d3d1ff61cb15833040ee3fd5cfc488e05775362dcde2
Tx public key: 088f039460fc0abf4ecd18b113c4fa7fde8eed2d986f75456d2ccfb2f8d81d87
Timestamp: 1729403226 Timestamp [UCT]: 2024-10-20 05:47:06 Age [y:d:h:m:s]: 00:170:04:19:01
Block: 1135507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121394 RingCT/type: yes/0
Extra: 01088f039460fc0abf4ecd18b113c4fa7fde8eed2d986f75456d2ccfb2f8d81d87021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 108d3ef2ce71697f8f49bfdd9e6ad04e79239f3cdbd106941a681caa0b52659b 0.600000000000 1618844 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": 1135517, "vin": [ { "gen": { "height": 1135507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "108d3ef2ce71697f8f49bfdd9e6ad04e79239f3cdbd106941a681caa0b52659b" } } ], "extra": [ 1, 8, 143, 3, 148, 96, 252, 10, 191, 78, 205, 24, 177, 19, 196, 250, 127, 222, 142, 237, 45, 152, 111, 117, 69, 109, 44, 207, 178, 248, 216, 29, 135, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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