Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64465ea174b06cb92bba282e3e4645aab8c307409f0b7c2136faec03568aa5e4

Tx prefix hash: f8d716c10140d10942096a83dc629e0b79522b8ead0dcdda62257d44043989c8
Tx public key: 3ab972cef0f9ac36c3351a6819ceb1d8894f9d732436012306105a3fe8e9cdc2
Timestamp: 1706249192 Timestamp [UCT]: 2024-01-26 06:06:32 Age [y:d:h:m:s]: 01:030:15:10:46
Block: 943524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282953 RingCT/type: yes/0
Extra: 013ab972cef0f9ac36c3351a6819ceb1d8894f9d732436012306105a3fe8e9cdc202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ead33777ea2f9308182e6ae9a8a8f94a57c1f7eda063aefc27dd9a3bd7cfeb 0.600000000000 1401732 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": 943534, "vin": [ { "gen": { "height": 943524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ead33777ea2f9308182e6ae9a8a8f94a57c1f7eda063aefc27dd9a3bd7cfeb" } } ], "extra": [ 1, 58, 185, 114, 206, 240, 249, 172, 54, 195, 53, 26, 104, 25, 206, 177, 216, 137, 79, 157, 115, 36, 54, 1, 35, 6, 16, 90, 63, 232, 233, 205, 194, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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