Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf7029d908632ac818fd12b5c05bede5b64fc946346b49d569c0425a2ae2f874

Tx prefix hash: 5f8f5319ab7f6eed61cb9f702571a394c179e2b0697cc70adfdc5ed40da06837
Tx public key: bb01328fac1584f6cd7673324c5d80cb349198ba9a3954495c6aca5db927d0c9
Timestamp: 1706977434 Timestamp [UCT]: 2024-02-03 16:23:54 Age [y:d:h:m:s]: 01:069:13:36:37
Block: 949572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310789 RingCT/type: yes/0
Extra: 01bb01328fac1584f6cd7673324c5d80cb349198ba9a3954495c6aca5db927d0c902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ad5ec947347cb32c595f6bed1edaf0e72c7b7b6d9b79cf7c71498a6e4cbeeff 0.600000000000 1408102 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": 949582, "vin": [ { "gen": { "height": 949572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ad5ec947347cb32c595f6bed1edaf0e72c7b7b6d9b79cf7c71498a6e4cbeeff" } } ], "extra": [ 1, 187, 1, 50, 143, 172, 21, 132, 246, 205, 118, 115, 50, 76, 93, 128, 203, 52, 145, 152, 186, 154, 57, 84, 73, 92, 106, 202, 93, 185, 39, 208, 201, 2, 17, 0, 0, 0, 2, 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