Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d909af74c9eb2870c6512f96adee6d09484fb1460ee5c83cdf71ec4d103900ae

Tx prefix hash: 867eb68e2a527dba8954c0cba2e77dc7b5b909b3f9935fb4048609c98bf292b2
Tx public key: 2fced1e33c02fbdcbf8650e6805b21a9939b38fef8cd28bfdfd12b7015ca75ec
Timestamp: 1704334222 Timestamp [UCT]: 2024-01-04 02:10:22 Age [y:d:h:m:s]: 01:315:17:55:18
Block: 927687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484487 RingCT/type: yes/0
Extra: 012fced1e33c02fbdcbf8650e6805b21a9939b38fef8cd28bfdfd12b7015ca75ec0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ccacfb4dd44c29650c6f5d57f3d0a12542df6347dec8bbe7acea684c69a7a13 0.600000000000 1385523 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": 927697, "vin": [ { "gen": { "height": 927687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ccacfb4dd44c29650c6f5d57f3d0a12542df6347dec8bbe7acea684c69a7a13" } } ], "extra": [ 1, 47, 206, 209, 227, 60, 2, 251, 220, 191, 134, 80, 230, 128, 91, 33, 169, 147, 155, 56, 254, 248, 205, 40, 191, 223, 209, 43, 112, 21, 202, 117, 236, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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