Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 506e632641784d666c31ef5a0815b0f31675f459f90aecba4980040e98a91ed7

Tx prefix hash: ab7c4af036e2fbc98955bdbc0df1161961907daaa77bd7e66b5e8d6584103521
Tx public key: ddd5ff322f26b0d96b4623a72b230f715c6a1b3d1eb44113843232479db91d47
Timestamp: 1711364892 Timestamp [UCT]: 2024-03-25 11:08:12 Age [y:d:h:m:s]: 01:229:04:43:26
Block: 985995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422469 RingCT/type: yes/0
Extra: 01ddd5ff322f26b0d96b4623a72b230f715c6a1b3d1eb44113843232479db91d470211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63b540360b8e2e3863bd2c0dd32ae2a3c5b40596828fcc07e07e47f1cdf8e1d3 0.600000000000 1446218 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": 986005, "vin": [ { "gen": { "height": 985995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63b540360b8e2e3863bd2c0dd32ae2a3c5b40596828fcc07e07e47f1cdf8e1d3" } } ], "extra": [ 1, 221, 213, 255, 50, 47, 38, 176, 217, 107, 70, 35, 167, 43, 35, 15, 113, 92, 106, 27, 61, 30, 180, 65, 19, 132, 50, 50, 71, 157, 185, 29, 71, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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