Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26f632be53a9cb55a594bc759ee27bd9365463ceb99b6f883278383e0148b0b3

Tx prefix hash: 5e0a0901c07fb89036cf0b9e6817e4ba61f5a292bcec0ed9e24fa6d8a6129118
Tx public key: 49f883e6aa31f59a7a14d1d87f2a6067237662776ab85659cc3a40d5184fca69
Timestamp: 1702708156 Timestamp [UCT]: 2023-12-16 06:29:16 Age [y:d:h:m:s]: 01:111:22:27:13
Block: 914194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341134 RingCT/type: yes/0
Extra: 0149f883e6aa31f59a7a14d1d87f2a6067237662776ab85659cc3a40d5184fca6902110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f585c6ae5d388cc04f1facc339f87f9ecf703cfa895fc1d3823402c1813bd39 0.600000000000 1371480 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": 914204, "vin": [ { "gen": { "height": 914194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f585c6ae5d388cc04f1facc339f87f9ecf703cfa895fc1d3823402c1813bd39" } } ], "extra": [ 1, 73, 248, 131, 230, 170, 49, 245, 154, 122, 20, 209, 216, 127, 42, 96, 103, 35, 118, 98, 119, 106, 184, 86, 89, 204, 58, 64, 213, 24, 79, 202, 105, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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