Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dead67e1a58aad8024c682dca42e4fcdcf25596cab9a46610ec206bff9252d6

Tx prefix hash: 237f3dd014a155c927f457e2b83b6900baeb49008c93d70d598de7821f1fe9fc
Tx public key: 8b2ecb0ee079200c51b2b377414b364746a4194d764dcab07be90e0896dd292c
Timestamp: 1699202895 Timestamp [UCT]: 2023-11-05 16:48:15 Age [y:d:h:m:s]: 01:137:07:00:26
Block: 885141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359307 RingCT/type: yes/0
Extra: 018b2ecb0ee079200c51b2b377414b364746a4194d764dcab07be90e0896dd292c021100000001faf35c9c000000000000000000

1 output(s) for total of 0.716408009000 dcy

stealth address amount amount idx
00: c3c089650dcb011eb22c04d56601a510e789a8f747e31dcb354f9ce441f5ebc4 0.716408009000 1340896 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": 885151, "vin": [ { "gen": { "height": 885141 } } ], "vout": [ { "amount": 716408009, "target": { "key": "c3c089650dcb011eb22c04d56601a510e789a8f747e31dcb354f9ce441f5ebc4" } } ], "extra": [ 1, 139, 46, 203, 14, 224, 121, 32, 12, 81, 178, 179, 119, 65, 75, 54, 71, 70, 164, 25, 77, 118, 77, 202, 176, 123, 233, 14, 8, 150, 221, 41, 44, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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