Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64429a5918d2262ccaa4c7bf13e2aab81dc8a9d39585b594f829c96b3391a5b6

Tx prefix hash: 9d3ae1425acfe2b8a07f9a004c555376b53cb6ac9043db4e53c8229b26f617f6
Tx public key: 29459fc6e8ce7a49dd9e7ed6aa3ae5e435e0749b2675f937adf0f0dbb1b41a3d
Timestamp: 1727614377 Timestamp [UCT]: 2024-09-29 12:52:57 Age [y:d:h:m:s]: 00:167:02:04:37
Block: 1120687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119230 RingCT/type: yes/0
Extra: 0129459fc6e8ce7a49dd9e7ed6aa3ae5e435e0749b2675f937adf0f0dbb1b41a3d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bdb741000ffd6dffe9cbda9f679bef21e7c026ef6e9b4d33eaa76e987123c3b 0.600000000000 1602692 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": 1120697, "vin": [ { "gen": { "height": 1120687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bdb741000ffd6dffe9cbda9f679bef21e7c026ef6e9b4d33eaa76e987123c3b" } } ], "extra": [ 1, 41, 69, 159, 198, 232, 206, 122, 73, 221, 158, 126, 214, 170, 58, 229, 228, 53, 224, 116, 155, 38, 117, 249, 55, 173, 240, 240, 219, 177, 180, 26, 61, 2, 17, 0, 0, 0, 1, 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