Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3de0a8fdc6a88f706e8a851cc744244b05314d1bcf2ce9d01f0fa45f67193bc

Tx prefix hash: 6d86af6006ea76c7634db7be72e59f3947f7298dceafaa25fd154864b7ef2e6d
Tx public key: 3177309b09a0e872ffac0641f31037b9129ecf3a9a236596cf901534d674d0e4
Timestamp: 1712100597 Timestamp [UCT]: 2024-04-02 23:29:57 Age [y:d:h:m:s]: 01:297:21:33:37
Block: 992031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471538 RingCT/type: yes/0
Extra: 013177309b09a0e872ffac0641f31037b9129ecf3a9a236596cf901534d674d0e40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f873909af34bb77860d162b751c88f338ee35adfc47e8856acd4979ddc239956 0.600000000000 1452367 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": 992041, "vin": [ { "gen": { "height": 992031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f873909af34bb77860d162b751c88f338ee35adfc47e8856acd4979ddc239956" } } ], "extra": [ 1, 49, 119, 48, 155, 9, 160, 232, 114, 255, 172, 6, 65, 243, 16, 55, 185, 18, 158, 207, 58, 154, 35, 101, 150, 207, 144, 21, 52, 214, 116, 208, 228, 2, 17, 0, 0, 0, 1, 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