Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42bbdd746fdb340dce66ef211880b3ac59bd562f75a9a2b4dc8efd320f5b79fd

Tx prefix hash: 30b566e60804ca47425e67f38baf7e0c1c338354f837262748e33a0f54d45bb5
Tx public key: d116e6aac55d43c01e690ba85488dd4b351f312ef2bb3667cdc85a059941593b
Timestamp: 1726645805 Timestamp [UCT]: 2024-09-18 07:50:05 Age [y:d:h:m:s]: 00:113:20:49:12
Block: 1112651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81419 RingCT/type: yes/0
Extra: 01d116e6aac55d43c01e690ba85488dd4b351f312ef2bb3667cdc85a059941593b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0c07811e7afbc6e8fa1e6aefa59a1d121a9e1fd48fe047f078cf39c4cb681f7 0.600000000000 1592046 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": 1112661, "vin": [ { "gen": { "height": 1112651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0c07811e7afbc6e8fa1e6aefa59a1d121a9e1fd48fe047f078cf39c4cb681f7" } } ], "extra": [ 1, 209, 22, 230, 170, 197, 93, 67, 192, 30, 105, 11, 168, 84, 136, 221, 75, 53, 31, 49, 46, 242, 187, 54, 103, 205, 200, 90, 5, 153, 65, 89, 59, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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