Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c3afdf8649079489b25fd732c24c9f1b41ec57e0180f3d75d96a6e23719ee16

Tx prefix hash: 3ac10c3a37e2ab96f3124d694cc9f35c702a1a984bc0a4a6a3bfb761eda839ac
Tx public key: eaae5b69772103855b40d1e26e109e6fb09366135d8f3d8c17f87df9010d2c71
Timestamp: 1583236776 Timestamp [UCT]: 2020-03-03 11:59:36 Age [y:d:h:m:s]: 04:257:15:25:28
Block: 75458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078512 RingCT/type: yes/0
Extra: 01eaae5b69772103855b40d1e26e109e6fb09366135d8f3d8c17f87df9010d2c7102110000001c724f989b000000000000000000

1 output(s) for total of 345.125555361000 dcy

stealth address amount amount idx
00: ddf2c48a7afeabd1bcfdb9fadb1821c1bde9ce7914be3306e56099758a2a7066 345.125555361000 139399 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": 75468, "vin": [ { "gen": { "height": 75458 } } ], "vout": [ { "amount": 345125555361, "target": { "key": "ddf2c48a7afeabd1bcfdb9fadb1821c1bde9ce7914be3306e56099758a2a7066" } } ], "extra": [ 1, 234, 174, 91, 105, 119, 33, 3, 133, 91, 64, 209, 226, 110, 16, 158, 111, 176, 147, 102, 19, 93, 143, 61, 140, 23, 248, 125, 249, 1, 13, 44, 113, 2, 17, 0, 0, 0, 28, 114, 79, 152, 155, 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