Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55911948cd6b85d7c1f1cb2a9bb50167a13ac11ccc470518fe3e3bdc6e9ef8a8

Tx prefix hash: eb31a3ea4ada2d7e4b5f1b6e8e6c63f8280cad9917405d6ebe14fc2780fd3852
Tx public key: e5974a799c06a245a68ce9e95769818c56eb7438eb3b67fd178a6e268d255212
Timestamp: 1716332658 Timestamp [UCT]: 2024-05-21 23:04:18 Age [y:d:h:m:s]: 00:318:08:19:35
Block: 1027151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227542 RingCT/type: yes/0
Extra: 01e5974a799c06a245a68ce9e95769818c56eb7438eb3b67fd178a6e268d25521202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deb2286b96c7c00bdb1cfdadacd1d9f451461f3d124f806caa140f4469b32616 0.600000000000 1494626 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": 1027161, "vin": [ { "gen": { "height": 1027151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deb2286b96c7c00bdb1cfdadacd1d9f451461f3d124f806caa140f4469b32616" } } ], "extra": [ 1, 229, 151, 74, 121, 156, 6, 162, 69, 166, 140, 233, 233, 87, 105, 129, 140, 86, 235, 116, 56, 235, 59, 103, 253, 23, 138, 110, 38, 141, 37, 82, 18, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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