Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60418a47ab8a59b0f3db836ca8667cdef21e84d3c48e0e4ed9716d4c1a3f51f0

Tx prefix hash: 916ba909012639f685e07ff9b2524035da7a968bfca3069b53e4578757cf8660
Tx public key: 3c1b1481f768ea1a9f1856826b44c7e9be252c426f8d63ee5c54f27171347cd2
Timestamp: 1732986645 Timestamp [UCT]: 2024-11-30 17:10:45 Age [y:d:h:m:s]: 00:114:05:21:20
Block: 1165124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81425 RingCT/type: yes/0
Extra: 013c1b1481f768ea1a9f1856826b44c7e9be252c426f8d63ee5c54f27171347cd2021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdf9c5823d335dc25bff8caee1010c149ea56c3969088bb5d95e65c3401ceb74 0.600000000000 1650799 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": 1165134, "vin": [ { "gen": { "height": 1165124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdf9c5823d335dc25bff8caee1010c149ea56c3969088bb5d95e65c3401ceb74" } } ], "extra": [ 1, 60, 27, 20, 129, 247, 104, 234, 26, 159, 24, 86, 130, 107, 68, 199, 233, 190, 37, 44, 66, 111, 141, 99, 238, 92, 84, 242, 113, 113, 52, 124, 210, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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