Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3dd5f236933305d48c682ce1608bb6c905849d60843429f3955fd85e72d6ca

Tx prefix hash: 6dd1cfb490f224ca3ac8c61fce81187818444442b8fbb113f80f09e0b37406f8
Tx public key: e2ffd6e80c4e51d47198acd5d3abbdcf00cfc93540cacfbae2a54876cdd1be10
Timestamp: 1707834714 Timestamp [UCT]: 2024-02-13 14:31:54 Age [y:d:h:m:s]: 01:055:00:56:06
Block: 956698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300376 RingCT/type: yes/0
Extra: 01e2ffd6e80c4e51d47198acd5d3abbdcf00cfc93540cacfbae2a54876cdd1be1002110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddbb21937ffa79ee281804e4c49d5f81e211262e72a50f20e0e3f6dd3d7db6da 0.600000000000 1416008 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": 956708, "vin": [ { "gen": { "height": 956698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddbb21937ffa79ee281804e4c49d5f81e211262e72a50f20e0e3f6dd3d7db6da" } } ], "extra": [ 1, 226, 255, 214, 232, 12, 78, 81, 212, 113, 152, 172, 213, 211, 171, 189, 207, 0, 207, 201, 53, 64, 202, 207, 186, 226, 165, 72, 118, 205, 209, 190, 16, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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