Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6caf7b0517de6fb85470f9dbf79c3f94b6135cb09c8d52d6bde8334bd31d06

Tx prefix hash: aa6e983eed851b962e9f7f648b5ae6973fa64d5210b14bb281d033ff34198ba0
Tx public key: b2c2f8da584051495f24ae5786135ba3cfc863310586267fa6d7de0cd30ad91d
Timestamp: 1706352259 Timestamp [UCT]: 2024-01-27 10:44:19 Age [y:d:h:m:s]: 01:309:16:07:26
Block: 944387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480157 RingCT/type: yes/0
Extra: 01b2c2f8da584051495f24ae5786135ba3cfc863310586267fa6d7de0cd30ad91d02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e593a5a3de8575ae0907acffee3ebbbca0d72e7039188cab0469d4b850a2cfd5 0.600000000000 1402623 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": 944397, "vin": [ { "gen": { "height": 944387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e593a5a3de8575ae0907acffee3ebbbca0d72e7039188cab0469d4b850a2cfd5" } } ], "extra": [ 1, 178, 194, 248, 218, 88, 64, 81, 73, 95, 36, 174, 87, 134, 19, 91, 163, 207, 200, 99, 49, 5, 134, 38, 127, 166, 215, 222, 12, 211, 10, 217, 29, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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