Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd82a19d38bd252205bc218ccf8868a351f79e0dff0a8f1cbb82f0169cb4b13

Tx prefix hash: fb6cf90d85a6ff5c6cc49cf4253a80081099eb23080636fb6911630548eb2f16
Tx public key: 2a7d342dc449801ee43f9e6236e0b2aa8a97d1c44172b72d17f159d4f19a3b1f
Timestamp: 1696772876 Timestamp [UCT]: 2023-10-08 13:47:56 Age [y:d:h:m:s]: 01:179:14:06:12
Block: 865204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389370 RingCT/type: yes/0
Extra: 012a7d342dc449801ee43f9e6236e0b2aa8a97d1c44172b72d17f159d4f19a3b1f021100000003bfa22221000000000000000000

1 output(s) for total of 0.834103645000 dcy

stealth address amount amount idx
00: 4aa03e06da81431e194fca760c15bdbc1a80921ac8192dccb22c6f81b281fc1f 0.834103645000 1319730 of 0

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": 865214, "vin": [ { "gen": { "height": 865204 } } ], "vout": [ { "amount": 834103645, "target": { "key": "4aa03e06da81431e194fca760c15bdbc1a80921ac8192dccb22c6f81b281fc1f" } } ], "extra": [ 1, 42, 125, 52, 45, 196, 73, 128, 30, 228, 63, 158, 98, 54, 224, 178, 170, 138, 151, 209, 196, 65, 114, 183, 45, 23, 241, 89, 212, 241, 154, 59, 31, 2, 17, 0, 0, 0, 3, 191, 162, 34, 33, 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