Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f89fca089fd8c055660f7cc842b32ec9d7d1dc42fcd69e44b9a9ea8e31503b6

Tx prefix hash: 43851aa748191f241c1af70b29e32bdd1a50a28455cf1144ce83cd92904b72da
Tx public key: b825bbcd2885c198e15d46587dada3522150d39f17d38c8b433160741d8254c5
Timestamp: 1733378683 Timestamp [UCT]: 2024-12-05 06:04:43 Age [y:d:h:m:s]: 01:055:04:43:12
Block: 1168367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297764 RingCT/type: yes/0
Extra: 01b825bbcd2885c198e15d46587dada3522150d39f17d38c8b433160741d8254c5021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4116437b0d126fe1ae1f1d1d0c9ca6452de30b35faf1043fb9ede94ea6f89f8d 0.600000000000 1654076 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": 1168377, "vin": [ { "gen": { "height": 1168367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4116437b0d126fe1ae1f1d1d0c9ca6452de30b35faf1043fb9ede94ea6f89f8d" } } ], "extra": [ 1, 184, 37, 187, 205, 40, 133, 193, 152, 225, 93, 70, 88, 125, 173, 163, 82, 33, 80, 211, 159, 23, 211, 140, 139, 67, 49, 96, 116, 29, 130, 84, 197, 2, 17, 0, 0, 0, 5, 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