Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d35f3386c4da602805feb6544f942e79c90283d8d8aa2b396bcc540f50f4668b

Tx prefix hash: 303e6d0b055baa50253b1321110a639fc5c9a3ed79037a0eeaad97e8d1520ea8
Tx public key: c857d769385474c0e5d390135ecb1f5fdd6a1569769e13bea8c66c8709dcc802
Timestamp: 1724119081 Timestamp [UCT]: 2024-08-20 01:58:01 Age [y:d:h:m:s]: 00:289:11:31:31
Block: 1091708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206813 RingCT/type: yes/0
Extra: 01c857d769385474c0e5d390135ecb1f5fdd6a1569769e13bea8c66c8709dcc80202110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 309589050792a730fd4261edbb6fc286ad7c06318301e59e38c5a927929015c2 0.600000000000 1566341 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": 1091718, "vin": [ { "gen": { "height": 1091708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "309589050792a730fd4261edbb6fc286ad7c06318301e59e38c5a927929015c2" } } ], "extra": [ 1, 200, 87, 215, 105, 56, 84, 116, 192, 229, 211, 144, 19, 94, 203, 31, 95, 221, 106, 21, 105, 118, 158, 19, 190, 168, 198, 108, 135, 9, 220, 200, 2, 2, 17, 0, 0, 0, 17, 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