Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbd25aaf9c51f8d3f58ea301e02fee17fb82fbbf010586362f12a10415c57029

Tx prefix hash: f699f2770f17f1457a8d9aad93cd0fb55fe30a22339349e93b4912d482726847
Tx public key: 54abd9f320ad8553391529a2d8654a55f85d1d4ea72cfe4dbfebd73a6022a2f0
Timestamp: 1588736311 Timestamp [UCT]: 2020-05-06 03:38:31 Age [y:d:h:m:s]: 04:344:23:41:07
Block: 98924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1162794 RingCT/type: yes/0
Extra: 0154abd9f320ad8553391529a2d8654a55f85d1d4ea72cfe4dbfebd73a6022a2f002110000000260e3cc90000000000000000000

1 output(s) for total of 288.552264011000 dcy

stealth address amount amount idx
00: 238000b61c2c33650b8391ec8dd794d83a935cd80b0bf241f17baa897de38b45 288.552264011000 174732 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": 98934, "vin": [ { "gen": { "height": 98924 } } ], "vout": [ { "amount": 288552264011, "target": { "key": "238000b61c2c33650b8391ec8dd794d83a935cd80b0bf241f17baa897de38b45" } } ], "extra": [ 1, 84, 171, 217, 243, 32, 173, 133, 83, 57, 21, 41, 162, 216, 101, 74, 85, 248, 93, 29, 78, 167, 44, 254, 77, 191, 235, 215, 58, 96, 34, 162, 240, 2, 17, 0, 0, 0, 2, 96, 227, 204, 144, 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