Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234a9a5ac2dd1a55c9ce082d8060161021512b7ebcad00a357b51cd0ef1e10f4

Tx prefix hash: e039bbae95efa432150d1fcbcd6031e2a754afd68d8961283c1de6ee627a446f
Tx public key: 32d79b8519c098ac3408d79bc246d8cdd5188b4d6da7be03ccf4ad775e602553
Timestamp: 1696827206 Timestamp [UCT]: 2023-10-09 04:53:26 Age [y:d:h:m:s]: 01:186:17:26:34
Block: 865651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394487 RingCT/type: yes/0
Extra: 0132d79b8519c098ac3408d79bc246d8cdd5188b4d6da7be03ccf4ad775e60255302110000000541ee1c9b000000000000000000

1 output(s) for total of 0.831263903000 dcy

stealth address amount amount idx
00: 301c551f0e85176ad73aa62abf55b3687ef25a60062dcd4ccf3a18556b2c4619 0.831263903000 1320189 of 0

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": 865661, "vin": [ { "gen": { "height": 865651 } } ], "vout": [ { "amount": 831263903, "target": { "key": "301c551f0e85176ad73aa62abf55b3687ef25a60062dcd4ccf3a18556b2c4619" } } ], "extra": [ 1, 50, 215, 155, 133, 25, 192, 152, 172, 52, 8, 215, 155, 194, 70, 216, 205, 213, 24, 139, 77, 109, 167, 190, 3, 204, 244, 173, 119, 94, 96, 37, 83, 2, 17, 0, 0, 0, 5, 65, 238, 28, 155, 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