Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faaea85b835490c2cf587c1d713cb1b8ebdde3b8b1754b69a8b009e3e3962e73

Tx prefix hash: c3282ce4b8ed8f5793fce62756225233a1c1a9c945031ad9283783c176082b5c
Tx public key: 85b601314eaa2ec840bf692c2c78f5c090cb6e791034204766f66e4c9efd8417
Timestamp: 1728253436 Timestamp [UCT]: 2024-10-06 22:23:56 Age [y:d:h:m:s]: 00:183:07:42:30
Block: 1125977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130806 RingCT/type: yes/0
Extra: 0185b601314eaa2ec840bf692c2c78f5c090cb6e791034204766f66e4c9efd8417021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d58831925112a947792bda386e91104ff231f50aa192587711c3105a244d5cb 0.600000000000 1608750 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": 1125987, "vin": [ { "gen": { "height": 1125977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d58831925112a947792bda386e91104ff231f50aa192587711c3105a244d5cb" } } ], "extra": [ 1, 133, 182, 1, 49, 78, 170, 46, 200, 64, 191, 105, 44, 44, 120, 245, 192, 144, 203, 110, 121, 16, 52, 32, 71, 102, 246, 110, 76, 158, 253, 132, 23, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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