Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955dd3c9b42a021766da346b2020d9b27150b8d68c68762795710953ffaf57ea

Tx prefix hash: 2b2889a943431c7e8c1215624ec3fc692c4704a3823e1c325a4e659b95d5fb2f
Tx public key: 1cdf8f9f4389901e9c7d42a1fd3c0bddc67eb60028b13fcb37ab6d6ef99a4bc0
Timestamp: 1700572008 Timestamp [UCT]: 2023-11-21 13:06:48 Age [y:d:h:m:s]: 01:348:01:59:05
Block: 896481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507660 RingCT/type: yes/0
Extra: 011cdf8f9f4389901e9c7d42a1fd3c0bddc67eb60028b13fcb37ab6d6ef99a4bc002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.657031647000 dcy

stealth address amount amount idx
00: 2027d08a312a95007410d1152aa466493f1a054fe09ef31c152497f9707a1e5b 0.657031647000 1352792 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": 896491, "vin": [ { "gen": { "height": 896481 } } ], "vout": [ { "amount": 657031647, "target": { "key": "2027d08a312a95007410d1152aa466493f1a054fe09ef31c152497f9707a1e5b" } } ], "extra": [ 1, 28, 223, 143, 159, 67, 137, 144, 30, 156, 125, 66, 161, 253, 60, 11, 221, 198, 126, 182, 0, 40, 177, 63, 203, 55, 171, 109, 110, 249, 154, 75, 192, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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