Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e39b794dba7d7a1658bef5bf9947b92761c95b1fefafef9a017cbafd9a00660

Tx prefix hash: c2034b957f0feefef0eea2bc9664833417ab4e6f2a72af2c985d5b716f81ec55
Tx public key: 667bd2ac7a5b28f7e81cdc255071dc276481eadef224cf40212e44eceff061aa
Timestamp: 1712343603 Timestamp [UCT]: 2024-04-05 19:00:03 Age [y:d:h:m:s]: 01:241:09:51:44
Block: 994046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431271 RingCT/type: yes/0
Extra: 01667bd2ac7a5b28f7e81cdc255071dc276481eadef224cf40212e44eceff061aa02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20e7f5ccfc442a877e4c0118c8cc630abde1f0a76a5598638831d43aa9efcc58 0.600000000000 1454442 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": 994056, "vin": [ { "gen": { "height": 994046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20e7f5ccfc442a877e4c0118c8cc630abde1f0a76a5598638831d43aa9efcc58" } } ], "extra": [ 1, 102, 123, 210, 172, 122, 91, 40, 247, 232, 28, 220, 37, 80, 113, 220, 39, 100, 129, 234, 222, 242, 36, 207, 64, 33, 46, 68, 236, 239, 240, 97, 170, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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