Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b5cee06d76d4b60e6f1637aad5f10d126bb03de3c8630f88b75eb2861a2e71d

Tx prefix hash: b1a4b9907989d67d189538e900eb487a5ec444bc72b2d81b4c0c07fbb3463c83
Tx public key: 41404ee00bfd093b29a4bf954511d1e27486ddbb645f115d5e8680b0ccccfd4e
Timestamp: 1708009153 Timestamp [UCT]: 2024-02-15 14:59:13 Age [y:d:h:m:s]: 01:049:20:36:31
Block: 958139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296676 RingCT/type: yes/0
Extra: 0141404ee00bfd093b29a4bf954511d1e27486ddbb645f115d5e8680b0ccccfd4e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bed6e03c93271647d92597a0efa5a6b5db406e8e4eba874eb6dbe05581f23939 0.600000000000 1417492 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": 958149, "vin": [ { "gen": { "height": 958139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bed6e03c93271647d92597a0efa5a6b5db406e8e4eba874eb6dbe05581f23939" } } ], "extra": [ 1, 65, 64, 78, 224, 11, 253, 9, 59, 41, 164, 191, 149, 69, 17, 209, 226, 116, 134, 221, 187, 100, 95, 17, 93, 94, 134, 128, 176, 204, 204, 253, 78, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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