Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b3e03cd3d77111899568a725a0bdbd78661e6fe9156b6f926151b4edf4918a9

Tx prefix hash: d116d53837310e6a9f9e7164d22f5dc98f5ab9091a1ee78686c36ebf65dbf61e
Tx public key: eca34574a6c31e396c52268730ea6f3d6f820fbf436c27044b400c7480f51923
Timestamp: 1703960855 Timestamp [UCT]: 2023-12-30 18:27:35 Age [y:d:h:m:s]: 01:055:09:36:42
Block: 924579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300668 RingCT/type: yes/0
Extra: 01eca34574a6c31e396c52268730ea6f3d6f820fbf436c27044b400c7480f51923021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66d275977a535accf60fb2e6db5aab52d6ea9e39d4d65101f9fa01e2c7aa7ae5 0.600000000000 1382333 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": 924589, "vin": [ { "gen": { "height": 924579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66d275977a535accf60fb2e6db5aab52d6ea9e39d4d65101f9fa01e2c7aa7ae5" } } ], "extra": [ 1, 236, 163, 69, 116, 166, 195, 30, 57, 108, 82, 38, 135, 48, 234, 111, 61, 111, 130, 15, 191, 67, 108, 39, 4, 75, 64, 12, 116, 128, 245, 25, 35, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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