Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c309996141111bd286110dbf468f29ec34f89b3c27fb7ec5a6e6df9a512f7cf

Tx prefix hash: 27af0d66e8d59a264b49570444c9316982fcf4ef67bf50a1cdd7ac2a0f2ab5ec
Tx public key: ddb86d1bbbaa0a0a9e445cc07511c4183d18d355e0a7c965de7b5b64ad074b11
Timestamp: 1710374722 Timestamp [UCT]: 2024-03-14 00:05:22 Age [y:d:h:m:s]: 01:007:22:01:25
Block: 977775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266626 RingCT/type: yes/0
Extra: 01ddb86d1bbbaa0a0a9e445cc07511c4183d18d355e0a7c965de7b5b64ad074b11021100000002a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45b4841e5e2e73db77ae7e9b562ef1391ba67759ae3cf7a8c7735d8f75b92a1d 0.600000000000 1437782 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": 977785, "vin": [ { "gen": { "height": 977775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45b4841e5e2e73db77ae7e9b562ef1391ba67759ae3cf7a8c7735d8f75b92a1d" } } ], "extra": [ 1, 221, 184, 109, 27, 187, 170, 10, 10, 158, 68, 92, 192, 117, 17, 196, 24, 61, 24, 211, 85, 224, 167, 201, 101, 222, 123, 91, 100, 173, 7, 75, 17, 2, 17, 0, 0, 0, 2, 165, 223, 157, 134, 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