Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f63c34f4a1b887f2ec9968fc90b5282d62f3894b8e29818a7941c3be0039da

Tx prefix hash: d6814a7fc1b0335d1227cc1e034c4b74279941c3876953c84f994bfe74298c25
Tx public key: 463e6b1f723918ce6f2648f4858b065a6b682fc9a27e349c89efdf40652a2733
Timestamp: 1735489808 Timestamp [UCT]: 2024-12-29 16:30:08 Age [y:d:h:m:s]: 00:104:11:26:28
Block: 1185837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74464 RingCT/type: yes/0
Extra: 01463e6b1f723918ce6f2648f4858b065a6b682fc9a27e349c89efdf40652a27330211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4250f723d7b41a0d45f1453578b4d67f908f0cc5dca1a4c32df8c4e627757747 0.600000000000 1672312 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": 1185847, "vin": [ { "gen": { "height": 1185837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4250f723d7b41a0d45f1453578b4d67f908f0cc5dca1a4c32df8c4e627757747" } } ], "extra": [ 1, 70, 62, 107, 31, 114, 57, 24, 206, 111, 38, 72, 244, 133, 139, 6, 90, 107, 104, 47, 201, 162, 126, 52, 156, 137, 239, 223, 64, 101, 42, 39, 51, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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