Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f5a6ff1b7e7b8ac03bd76486ac93aa1770e52db3139e8f58d40460797259b3f

Tx prefix hash: e6289a522ce3617f053bc6734f175299ef42efb8d1d2079a93ccca6ae3216cc4
Tx public key: 7f8e855a2696cad6468b0258ee268f728c9ff6ca6d73f6cc18aa0057a549ab0f
Timestamp: 1717574015 Timestamp [UCT]: 2024-06-05 07:53:35 Age [y:d:h:m:s]: 01:152:01:02:32
Block: 1037457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367225 RingCT/type: yes/0
Extra: 017f8e855a2696cad6468b0258ee268f728c9ff6ca6d73f6cc18aa0057a549ab0f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f2ca482ddd125dbb9d22de38e3d51bb2dbc0a9d9cae9d22ee38738b020bedc8 0.600000000000 1505990 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": 1037467, "vin": [ { "gen": { "height": 1037457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f2ca482ddd125dbb9d22de38e3d51bb2dbc0a9d9cae9d22ee38738b020bedc8" } } ], "extra": [ 1, 127, 142, 133, 90, 38, 150, 202, 214, 70, 139, 2, 88, 238, 38, 143, 114, 140, 159, 246, 202, 109, 115, 246, 204, 24, 170, 0, 87, 165, 73, 171, 15, 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