Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28d6adc1c2936122f57de14a4eb79681218eb017c1676e2df7961cec8be33a7

Tx prefix hash: b6c52465ed46e05be0e1ae6824554e8e8176e2c35b968eea11cb1884e42a8f22
Tx public key: 88e511cb7d234fadfa5116449728d8b7e42ddc24d972a3e19be8f2ac1b6cd424
Timestamp: 1725120533 Timestamp [UCT]: 2024-08-31 16:08:53 Age [y:d:h:m:s]: 00:084:15:27:15
Block: 1099998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60543 RingCT/type: yes/0
Extra: 0188e511cb7d234fadfa5116449728d8b7e42ddc24d972a3e19be8f2ac1b6cd42402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08cef75bdc51e1b8bc7c1c5311b3203f0549fb0c4f18eaf01cb2490213cb8416 0.600000000000 1575969 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": 1100008, "vin": [ { "gen": { "height": 1099998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08cef75bdc51e1b8bc7c1c5311b3203f0549fb0c4f18eaf01cb2490213cb8416" } } ], "extra": [ 1, 136, 229, 17, 203, 125, 35, 79, 173, 250, 81, 22, 68, 151, 40, 216, 183, 228, 45, 220, 36, 217, 114, 163, 225, 155, 232, 242, 172, 27, 108, 212, 36, 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