Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4348ecd694a0a3d6cfe15df1b5ce1aaf3aa1020d1cfe15a95c52d0bd3064617c

Tx prefix hash: 2719207465107273eb879f4ac9d545da80652446413a233808d4cac78f639373
Tx public key: 159f96e2385fcb0fa22341f830631ce01c1fb84eb2323ce68c8feb76fbc7e1ac
Timestamp: 1732987305 Timestamp [UCT]: 2024-11-30 17:21:45 Age [y:d:h:m:s]: 00:106:08:34:54
Block: 1165133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75814 RingCT/type: yes/0
Extra: 01159f96e2385fcb0fa22341f830631ce01c1fb84eb2323ce68c8feb76fbc7e1ac021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28f2cf7c124687a1c777f03735b3c4f742805585adf3d7ab3b08ae00f0f27eb3 0.600000000000 1650808 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": 1165143, "vin": [ { "gen": { "height": 1165133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28f2cf7c124687a1c777f03735b3c4f742805585adf3d7ab3b08ae00f0f27eb3" } } ], "extra": [ 1, 21, 159, 150, 226, 56, 95, 203, 15, 162, 35, 65, 248, 48, 99, 28, 224, 28, 31, 184, 78, 178, 50, 60, 230, 140, 143, 235, 118, 251, 199, 225, 172, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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