Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99a5705469d68c51933b88c0ce85eedf781da96776b08c47e8e2fe36058d0b5d

Tx prefix hash: 35fbcc7241ef7729b5aa7e1b2e17a545f10b0b4e8a668655a9d1d1644a3611f5
Tx public key: a42f359529e8e8b94ee42f489e1fc24e007ff10d6b635ff49670670df3c86061
Timestamp: 1716932141 Timestamp [UCT]: 2024-05-28 21:35:41 Age [y:d:h:m:s]: 00:210:06:50:44
Block: 1032136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150501 RingCT/type: yes/0
Extra: 01a42f359529e8e8b94ee42f489e1fc24e007ff10d6b635ff49670670df3c8606102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 931a2678558ecb12f83cf4c7c57fd0542e56dc09edc390dc2a1236b923e36962 0.600000000000 1500585 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": 1032146, "vin": [ { "gen": { "height": 1032136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "931a2678558ecb12f83cf4c7c57fd0542e56dc09edc390dc2a1236b923e36962" } } ], "extra": [ 1, 164, 47, 53, 149, 41, 232, 232, 185, 78, 228, 47, 72, 158, 31, 194, 78, 0, 127, 241, 13, 107, 99, 95, 244, 150, 112, 103, 13, 243, 200, 96, 97, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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