Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f1fb3672942d0b979d0503cb6de37db55ede62198ac8395b0e638fa83bf192

Tx prefix hash: cf0d7433fa911ce2e0589ad32f20e230afaccaee90331b04d44b37dc5a0ee17c
Tx public key: fcf78f1d176c3b7d28fcf7836dced0f897d9a061ba35b98aae78028448c7d262
Timestamp: 1727066650 Timestamp [UCT]: 2024-09-23 04:44:10 Age [y:d:h:m:s]: 00:235:09:51:11
Block: 1116143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168086 RingCT/type: yes/0
Extra: 01fcf78f1d176c3b7d28fcf7836dced0f897d9a061ba35b98aae78028448c7d26202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3519262f77ed755cf2e9c42fcab7adccf14182e5e4ef6da56f7778a678f1c16a 0.600000000000 1596522 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": 1116153, "vin": [ { "gen": { "height": 1116143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3519262f77ed755cf2e9c42fcab7adccf14182e5e4ef6da56f7778a678f1c16a" } } ], "extra": [ 1, 252, 247, 143, 29, 23, 108, 59, 125, 40, 252, 247, 131, 109, 206, 208, 248, 151, 217, 160, 97, 186, 53, 185, 138, 174, 120, 2, 132, 72, 199, 210, 98, 2, 17, 0, 0, 0, 2, 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