Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dcaefea8e338978ca6a2776a56538a0939f91251697a6ba2dc1ef884d8fa7b5

Tx prefix hash: 02be282e9dc9d503599413f62423e421d0696bb1c56a89c5bbdcb70e7f3425dc
Tx public key: 95f99c66ab9a94626ed3e45546c9674712d6082a75087f686ba17cb481419de8
Timestamp: 1726874054 Timestamp [UCT]: 2024-09-20 23:14:14 Age [y:d:h:m:s]: 00:206:09:15:41
Block: 1114543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147329 RingCT/type: yes/0
Extra: 0195f99c66ab9a94626ed3e45546c9674712d6082a75087f686ba17cb481419de80211000000012c3a34dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7337fcf127e88e2928e7b8fb705f5b23cecaf4ff1b298c302550adf97d5c266c 0.600000000000 1594360 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": 1114553, "vin": [ { "gen": { "height": 1114543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7337fcf127e88e2928e7b8fb705f5b23cecaf4ff1b298c302550adf97d5c266c" } } ], "extra": [ 1, 149, 249, 156, 102, 171, 154, 148, 98, 110, 211, 228, 85, 70, 201, 103, 71, 18, 214, 8, 42, 117, 8, 127, 104, 107, 161, 124, 180, 129, 65, 157, 232, 2, 17, 0, 0, 0, 1, 44, 58, 52, 220, 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