Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6344795032b10f5ed7b83484620fbd4d256e6ac0252c53f783eed55f4bdf329

Tx prefix hash: 45f5e31e1b938af0094d474add9ad91edca8ec9100ea50b125ac9e94e269baec
Tx public key: e82db0817eabe48c827976f83197d781d46a4430d26b5e9a24be9a0333ee9c7e
Timestamp: 1696117549 Timestamp [UCT]: 2023-09-30 23:45:49 Age [y:d:h:m:s]: 01:237:02:34:07
Block: 859760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430552 RingCT/type: yes/0
Extra: 01e82db0817eabe48c827976f83197d781d46a4430d26b5e9a24be9a0333ee9c7e02110000000d4b8f5122000000000000000000

1 output(s) for total of 0.869547322000 dcy

stealth address amount amount idx
00: 3805a5d30c9309078b44500b2a17f260b81c238566eb8e3e350bdaaba725b734 0.869547322000 1314004 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": 859770, "vin": [ { "gen": { "height": 859760 } } ], "vout": [ { "amount": 869547322, "target": { "key": "3805a5d30c9309078b44500b2a17f260b81c238566eb8e3e350bdaaba725b734" } } ], "extra": [ 1, 232, 45, 176, 129, 126, 171, 228, 140, 130, 121, 118, 248, 49, 151, 215, 129, 212, 106, 68, 48, 210, 107, 94, 154, 36, 190, 154, 3, 51, 238, 156, 126, 2, 17, 0, 0, 0, 13, 75, 143, 81, 34, 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