Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fa48c76883707eeae4027f1ba2b55d9de022832a9b85321933181ebc49ceb36

Tx prefix hash: 5ed608a75cee224705d9f1bfab1a48ae8fa9a0ae9726582a2d7dab26102fcb7b
Tx public key: 58696400b3ae4ba2e386c2b8fa2eb7afca978cbe38d04540c0db77af02e87e3c
Timestamp: 1669684705 Timestamp [UCT]: 2022-11-29 01:18:25 Age [y:d:h:m:s]: 02:178:20:24:34
Block: 641319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649567 RingCT/type: yes/0
Extra: 0158696400b3ae4ba2e386c2b8fa2eb7afca978cbe38d04540c0db77af02e87e3c02110000000275e3f0e9000000000000000000

1 output(s) for total of 4.603031300000 dcy

stealth address amount amount idx
00: 2106f9f32485045c6dfe64b0db2f80c6d9fcb1b7d8b2639e5a44e9edf2ce3477 4.603031300000 1081114 of 0

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": 641329, "vin": [ { "gen": { "height": 641319 } } ], "vout": [ { "amount": 4603031300, "target": { "key": "2106f9f32485045c6dfe64b0db2f80c6d9fcb1b7d8b2639e5a44e9edf2ce3477" } } ], "extra": [ 1, 88, 105, 100, 0, 179, 174, 75, 162, 227, 134, 194, 184, 250, 46, 183, 175, 202, 151, 140, 190, 56, 208, 69, 64, 192, 219, 119, 175, 2, 232, 126, 60, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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