Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b370274ab2a257833d7b2bbc4afad78e40706c34496a4ef49fdb2180340336c8

Tx prefix hash: f2e29749a349f805fe79882939666f21e3571218ac73be65dc00c6c61dd8491b
Tx public key: 14f57fb43a3e5b7dc6f02473561b4d7a8b8b6ec562f54ddf87a3378fc7709861
Timestamp: 1731251156 Timestamp [UCT]: 2024-11-10 15:05:56 Age [y:d:h:m:s]: 00:126:00:43:16
Block: 1150749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89896 RingCT/type: yes/0
Extra: 0114f57fb43a3e5b7dc6f02473561b4d7a8b8b6ec562f54ddf87a3378fc77098610211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b64ffa526b22f7bba9317e346a498204e04f96e3d9b7c990d29adf2a1fc3827 0.600000000000 1636134 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": 1150759, "vin": [ { "gen": { "height": 1150749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b64ffa526b22f7bba9317e346a498204e04f96e3d9b7c990d29adf2a1fc3827" } } ], "extra": [ 1, 20, 245, 127, 180, 58, 62, 91, 125, 198, 240, 36, 115, 86, 27, 77, 122, 139, 139, 110, 197, 98, 245, 77, 223, 135, 163, 55, 143, 199, 112, 152, 97, 2, 17, 0, 0, 0, 4, 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