Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50600cbcf19f34a7fa939a95e0548c0373dda8fb94e59e26d4a5259436e72df0

Tx prefix hash: 565fcddec691af9573a4b73fdf8c6bb677e2ae0ba9514765a1198a2d7ec21a73
Tx public key: 2fe5426908b56cefce05a0a9581ce1884f90ad74be50e019e52ecaa18af64c33
Timestamp: 1701375170 Timestamp [UCT]: 2023-11-30 20:12:50 Age [y:d:h:m:s]: 01:130:00:51:09
Block: 903144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354091 RingCT/type: yes/0
Extra: 012fe5426908b56cefce05a0a9581ce1884f90ad74be50e019e52ecaa18af64c33021100000001679a8a81000000000000000000

1 output(s) for total of 0.624466282000 dcy

stealth address amount amount idx
00: f9f5b807d2eb04f27dc3c58e00f5dd3f96d10ec2332ececb63dfb151524f6db9 0.624466282000 1359811 of 0

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": 903154, "vin": [ { "gen": { "height": 903144 } } ], "vout": [ { "amount": 624466282, "target": { "key": "f9f5b807d2eb04f27dc3c58e00f5dd3f96d10ec2332ececb63dfb151524f6db9" } } ], "extra": [ 1, 47, 229, 66, 105, 8, 181, 108, 239, 206, 5, 160, 169, 88, 28, 225, 136, 79, 144, 173, 116, 190, 80, 224, 25, 229, 46, 202, 161, 138, 246, 76, 51, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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