Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b555e61527257f56907d8699981e27f0d2beba29683d72c56773ae8df9c4f8

Tx prefix hash: b44a30e2cc571685dbeb96de96c8d3043a6bd6840b6fde2774b4c2f8505767fc
Tx public key: e975c7681dced283b800ec2aa24a6f8798d5eb177adba1a57a2b8e4de8014c9e
Timestamp: 1710917285 Timestamp [UCT]: 2024-03-20 06:48:05 Age [y:d:h:m:s]: 00:312:21:44:11
Block: 982273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223725 RingCT/type: yes/0
Extra: 01e975c7681dced283b800ec2aa24a6f8798d5eb177adba1a57a2b8e4de8014c9e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8bc7ceaeb6ca6336c84a6a457274e9dcf1bc392fe77c76cb7c0ede0a833212e 0.600000000000 1442378 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": 982283, "vin": [ { "gen": { "height": 982273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8bc7ceaeb6ca6336c84a6a457274e9dcf1bc392fe77c76cb7c0ede0a833212e" } } ], "extra": [ 1, 233, 117, 199, 104, 29, 206, 210, 131, 184, 0, 236, 42, 162, 74, 111, 135, 152, 213, 235, 23, 122, 219, 161, 165, 122, 43, 142, 77, 232, 1, 76, 158, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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