Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747dc5e26547f212b265d84f05db6a297d873ad6ec95e586269a4a13ae2d3d54

Tx prefix hash: 7d7f06c43474fdb54a10835912d1e4a4ba369c1f25e506cd75659823cb0a88e7
Tx public key: 7546adec4d0dcb96b9c555a86fa36eddca6aaa4c22496a10486a2740b448054c
Timestamp: 1725764607 Timestamp [UCT]: 2024-09-08 03:03:27 Age [y:d:h:m:s]: 00:121:07:47:34
Block: 1105353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86759 RingCT/type: yes/0
Extra: 017546adec4d0dcb96b9c555a86fa36eddca6aaa4c22496a10486a2740b448054c02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83803644f50b34c9d22ec79483c4c2d12afc2ad8f20c9f0f939d17d5547d5fa3 0.600000000000 1582694 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": 1105363, "vin": [ { "gen": { "height": 1105353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83803644f50b34c9d22ec79483c4c2d12afc2ad8f20c9f0f939d17d5547d5fa3" } } ], "extra": [ 1, 117, 70, 173, 236, 77, 13, 203, 150, 185, 197, 85, 168, 111, 163, 110, 221, 202, 106, 170, 76, 34, 73, 106, 16, 72, 106, 39, 64, 180, 72, 5, 76, 2, 17, 0, 0, 0, 7, 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