Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95e42b14937a7b41eb4ccc7f62c4e0e275b46208f97039760c9a99860af7247b

Tx prefix hash: 8dfce01ac1b9541975a3350bc51ce8ce80886293984399819ecd2b046e071d02
Tx public key: 43f5aa93b4eb63b68f635f7980987307d850c7845a75ea1ade2b919a9d204665
Timestamp: 1736390372 Timestamp [UCT]: 2025-01-09 02:39:32 Age [y:d:h:m:s]: 00:160:14:30:54
Block: 1193307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114485 RingCT/type: yes/0
Extra: 0143f5aa93b4eb63b68f635f7980987307d850c7845a75ea1ade2b919a9d204665021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9de977b4e1c4f9625b0e45dc9b2e7ae85e8f7a4ffb764b7ddc12fc6abdbcc0 0.600000000000 1679866 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": 1193317, "vin": [ { "gen": { "height": 1193307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9de977b4e1c4f9625b0e45dc9b2e7ae85e8f7a4ffb764b7ddc12fc6abdbcc0" } } ], "extra": [ 1, 67, 245, 170, 147, 180, 235, 99, 182, 143, 99, 95, 121, 128, 152, 115, 7, 216, 80, 199, 132, 90, 117, 234, 26, 222, 43, 145, 154, 157, 32, 70, 101, 2, 17, 0, 0, 0, 9, 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