Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e322c5656b4e990a28164f803ae4d09c99fe82da7d3952a099c07b707bc04e

Tx prefix hash: 5a3606d6a7f1fd884124373b4aeceb2c0081c57ce2b0056f7d4a11496046d81d
Tx public key: c312f13efa4ef77a6395adba0b77a2f6986507320e599408e3f8786abe162f53
Timestamp: 1704965884 Timestamp [UCT]: 2024-01-11 09:38:04 Age [y:d:h:m:s]: 01:122:02:40:41
Block: 932904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348397 RingCT/type: yes/0
Extra: 01c312f13efa4ef77a6395adba0b77a2f6986507320e599408e3f8786abe162f530211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47c3b08d36cc5b741c47091d61eb223c377cbc2a02c27b0d7b949bc95b86b242 0.600000000000 1390844 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": 932914, "vin": [ { "gen": { "height": 932904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47c3b08d36cc5b741c47091d61eb223c377cbc2a02c27b0d7b949bc95b86b242" } } ], "extra": [ 1, 195, 18, 241, 62, 250, 78, 247, 122, 99, 149, 173, 186, 11, 119, 162, 246, 152, 101, 7, 50, 14, 89, 148, 8, 227, 248, 120, 106, 190, 22, 47, 83, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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