Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7997a905df43d2183236e3e56a098d23f844723825c67db3bc4319a2effb3d

Tx prefix hash: de771006879fca024298f94e16c9e59d75390b8b589eb3f373b6d24dc1596b23
Tx public key: d3eefc2bf2a6413a5654476b2504dc104d6ec5f8bee13b4de845ada0141e2869
Timestamp: 1739337537 Timestamp [UCT]: 2025-02-12 05:18:57 Age [y:d:h:m:s]: 00:351:09:18:59
Block: 1217440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248803 RingCT/type: yes/0
Extra: 01d3eefc2bf2a6413a5654476b2504dc104d6ec5f8bee13b4de845ada0141e2869021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e957d290f680624efd78597d7f1a99a6f7065941c64eb190d0fc3a4d66f3d51 0.600000000000 1704253 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": 1217450, "vin": [ { "gen": { "height": 1217440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e957d290f680624efd78597d7f1a99a6f7065941c64eb190d0fc3a4d66f3d51" } } ], "extra": [ 1, 211, 238, 252, 43, 242, 166, 65, 58, 86, 84, 71, 107, 37, 4, 220, 16, 77, 110, 197, 248, 190, 225, 59, 77, 232, 69, 173, 160, 20, 30, 40, 105, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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