Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1adf1a38872528d7e63dfc4a2ab66d2722e8b8e1c915a0aeb134f7246edaece0

Tx prefix hash: c05a67ce56f156ab4c1e29737e2a5ad78319a8286ea3ec31b3271d9e440612c6
Tx public key: 50f078ce95f66c6ffa1cbdeeb4f55079f9b5860b78c75a2c0d5544983b2e9671
Timestamp: 1722861381 Timestamp [UCT]: 2024-08-05 12:36:21 Age [y:d:h:m:s]: 00:170:16:15:52
Block: 1081276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122064 RingCT/type: yes/0
Extra: 0150f078ce95f66c6ffa1cbdeeb4f55079f9b5860b78c75a2c0d5544983b2e9671021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1afb62e2cee9f6226ee217393fe453b4712015da81324e2927c73696ee7e1b22 0.600000000000 1554959 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": 1081286, "vin": [ { "gen": { "height": 1081276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1afb62e2cee9f6226ee217393fe453b4712015da81324e2927c73696ee7e1b22" } } ], "extra": [ 1, 80, 240, 120, 206, 149, 246, 108, 111, 250, 28, 189, 238, 180, 245, 80, 121, 249, 181, 134, 11, 120, 199, 90, 44, 13, 85, 68, 152, 59, 46, 150, 113, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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