Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3b33a9c83a8306d9db8d8f9a12f17ee5ff44b7c97eb5cff93308f36f0797d9

Tx prefix hash: 61b30a28f31d8e8ecddda0ce0af219e4f7cf9abb64af315660a2c1bad5ef57b5
Tx public key: 1a91f6a74cd130b73a726ca6e667731ca83ab9e842cf35b1ae759de356d0069a
Timestamp: 1728310696 Timestamp [UCT]: 2024-10-07 14:18:16 Age [y:d:h:m:s]: 00:216:06:01:43
Block: 1126458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154371 RingCT/type: yes/0
Extra: 011a91f6a74cd130b73a726ca6e667731ca83ab9e842cf35b1ae759de356d0069a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443bf170393cbeb2fad53c65a599916c074c92e2ea23148047789304906077b5 0.600000000000 1609251 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": 1126468, "vin": [ { "gen": { "height": 1126458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443bf170393cbeb2fad53c65a599916c074c92e2ea23148047789304906077b5" } } ], "extra": [ 1, 26, 145, 246, 167, 76, 209, 48, 183, 58, 114, 108, 166, 230, 103, 115, 28, 168, 58, 185, 232, 66, 207, 53, 177, 174, 117, 157, 227, 86, 208, 6, 154, 2, 17, 0, 0, 0, 4, 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